An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hello, My app update has been in "Waiting for Review" for over 100 hours and has never moved to "In Review". There are no messages in the Resolution Center and no requests for additional information. Details: • App: DEADGRID • Apple ID: 6790152649 • Platform: iOS • Version: 1.9 (update — 1.8 is live and was reviewed without issue) • Build: 29750736 • Submitted: July 26, 2026 • Current status: Waiting for Review • Developer Support case number: 20000123502103 This is an update to an existing, previously approved app. Agreements, Tax and Banking are all active, and all version metadata, export compliance and age rating information is complete. Nothing has changed on my side since submission. Could someone confirm whether the submission is proceeding normally or whether any action is required from me? I have already sent emails in multiple days but no answer. Thank you and best regards, Afonso Quinaz

Hello, My app update has been in "Waiting for Review" for over 100 hours and has never moved to "In Review". There are no messages in the Resolution Center and no requests for additional information. I have already sent emails in multiple days but no answer. Details: • Apple ID: 6787716218 • Platform: iOS • Version: 1.0.1 (update — 1.0 is live and was reviewed without issue) • Build: 7 • Submitted: July 26, 2026 • Current status: Waiting for Review • Developer Support case number: 102937394456 This is an update to an existing, previously approved app. Agreements, Tax and Banking are all active, and all version metadata, export compliance and age rating information is complete. Nothing has changed on my side since submission. Could someone confirm whether the submission is proceeding normally or whether any action is required from me? Thank you and best regards, Eric

I need practical guidance from developers who have successfully handled a Guideline 4.3(b) rejection, especially for an astrology-related app with broader personalized features. I mainly want to understand how to present the app, write the App Store description and Review Notes, choose screenshots, and decide whether to reply in the Resolution Center or file an appeal. My app was rejected because Apple said there are already many astrology apps on the App Store. However, it is not designed as a standard horoscope or prediction app. Its main experience focuses on personal milestones, AI-powered questions, relationship compatibility, private social connections, and a personalized user journey. Planetary positions are used only as one supporting input in the backend to provide contextual insights. They are not the main purpose of the app. Has anyone successfully handled a similar rejection? Any real experience or practical advice would be very helpful.

Hi everyone, We're experiencing an unusually long App Review delay for our tvOS application and wanted to check if anyone else is seeing the same behaviour or has any suggestions. App Details Platform: tvOS Xcode Version: 26.4.1 Submission Type: App Update Distribution: App Store Status: In Review Issue We submitted an app update last week, and it remained in the "In Review" state for approximately one week with no updates. Since there was no progress, we rejected that submission, uploaded a new build, and submitted it again. The new build has now also been "In Review" for the last 5 days. Apple has not rejected the app or provided any review notes or requests for additional information. The status simply remains "In Review". What we've tried Submitted an Expedited Review Request. Contacted Apple using the App Review "Contact Us" option. We have not received any response to either request. Since there is no rejection or feedback, we don't have any indication that there is an issue with the app itself. Questions Is anyone else currently experiencing unusually long review times for tvOS apps? Is this likely to be an App Review backlog or a known issue on Apple's side? Has anyone had success getting a response through App Review support or Developer Support in a similar situation? Is there anything else we can do besides waiting? Any insights or recent experiences would be greatly appreciated. Thank you!

Team ID: 63XFUNLKTY App: TabUp Build: 1.0.0(10) Submission ID: 43c1231c-7b80-44c6-91af-f45aff050530 -- It has now been more than 56 working business hours since I submitted my build for review, and the submission is still showing "Waiting for Review." My Agreements, Tax, and Banking information are all active, and all required metadata, privacy details, age rating, and export compliance information have been completed. I've also spent over two hours on hold with Developer Support without being able to speak to anyone or get an update on the status of my submission. I invested a significant amount of time building this app, and the lack of any progress, feedback, or estimated review timeframe has been extremely frustrating. As an independent developer, delays like this directly affect my ability to launch, gather user feedback, and begin generating revenue. I understand that review times can vary, but this delay seems unusually long compared with Apple's published expectations. Is there anything that could be causing a submission to remain stuck for this long? Any guidance from Apple or other developers who have experienced this would be appreciated. Thank you :)

My app already has an approved subscription group with approved monthly and annual subscriptions. I later submitted a new non-consumable in-app purchase with an app version. App Review rejected the submission because the paywall also displays the existing subscriptions, stating that the subscriptions had not been submitted for review. However, App Store Connect will not let me add the approved subscriptions to the submission because they are already in Approved status and the Add for Review button is disabled. At this point I'm unsure what corrective action App Review expects. I've replied through the App Review message thread requesting clarification, but I have never received a response to messages sent through App Review. I also attempted to contact Apple Developer Support through the Dispute App Rejection support option, but after waiting on hold for over two hours I was still unable to reach anyone. Has anyone encountered this workflow before? Is there a way to include previously approved subscriptions in a new review that I'm missing, or does this require App Review to resolve internally?

Im trying to add my build for review yet there is no upload option listed. does anyone have any suggestions or experience with this if so what did you do to res this proble?

Our app sells two auto-renewable subscriptions. Product loading succeeds and returns both products with correct localized prices, but every purchase attempt fails roughly one second later with "Item Unavailable". No purchase sheet is ever presented to the user. The app has not yet passed its first App Review. It was rejected under Guideline 2.1(b) because the reviewer encountered this same error on their device. MY QUESTION Under what conditions does StoreKit reject a purchase with "Item Unavailable" for a product that has just been returned successfully, with a valid localized price, by a product request? Is an auto-renewable subscription transactable in the sandbox environment for an app that has never had a binary approved by App Review? Question 2 is the one I most need answered. App Review's rejection states that In-App Purchase products "do not need prior approval to function in review", but neither we nor the reviewer can transact them. DIAGNOSTIC LOG Captured on-device during a failing session: 01:08:56 fetchProducts [com.aurascanner.app.pro.weekly, com.aurascanner.app.pro.annual] 01:08:56 fetchProducts -> 2 product(s): com.aurascanner.app.pro.annual=$39.99; com.aurascanner.app.pro.weekly=$6.99 01:08:56 requestPurchase sku=com.aurascanner.app.pro.weekly 01:08:57 purchaseError: code=purchase-error msg=Item Unavailable 01:08:57 error code=purchase-error, storefront=USA 01:09:05 fetchProducts -> 2 product(s), same prices returned again 01:09:05 requestPurchase sku=com.aurascanner.app.pro.annual 01:09:06 requestPurchase threw: Item Unavailable 01:09:06 error code=purchase-error, storefront=USA An introductory-offer eligibility check earlier in the session also succeeded, using the subscription group ID read from the loaded product. So product metadata, including the subscription group, resolves correctly. CONDITIONS Fails identically for both products, on every attempt. Reproduces in TestFlight on our own devices and Apple IDs. Also failed during App Review on iPad Air 11-inch (M3), iPadOS 26.5.2. Storefront reports as USA in every case. Real devices only. Not reproduced on Simulator. ALREADY VERIFIED Paid Applications Agreement: Active, banking and tax information complete. In-App Purchase capability: enabled on the App ID at Certificates, Identifiers & Profiles. Bundle identifier com.aurascanner.app matches the App Store Connect record. Both subscriptions: complete metadata, review screenshots uploaded, USD pricing set, United States availability. Both subscriptions and the subscription group are attached to the current submission, status "Ready for Review". Subscription group has a localized display name. Build distributed via TestFlight, which routes purchases to sandbox automatically. IMPLEMENTATION The app is React Native and uses a wrapper library over StoreKit 2, but the error text originates from StoreKit rather than the wrapper, and the call order follows the documented pattern: Initialize the StoreKit connection. Load products. This succeeds and returns both products. Register transaction update and error listeners. Request the purchase. This is where it fails. Purchases are verified server-side using Apple's App Store Server Library, and the transaction is finished only after verification succeeds. I am not asking anyone to debug the wrapper. My question is about StoreKit and App Store behaviour: what causes the store to quote a product and then decline to sell it? Any pointers appreciated. I can supply screenshots or the full log.

Hello App Review team - I am an iOS developer and my app(App ID: 6756242440) is stuck in 'Waiting for review'. Please help us resolve the issue. Thanks in advance!

Hi everyone, Has anyone had an app version approved while the subscriptions submitted alongside it were left behind in review? I submitted a new version of my app together with two replacement auto-renewable subscriptions. The app itself was approved yesterday, but both subscriptions still show Waiting for Review. Both subscriptions are fully configured, connected through RevenueCat and work correctly in TestFlight. However, because they have not been approved for production, the live app cannot load the plans and users cannot start a trial or subscribe. This follows a previous issue where my original monthly and annual subscriptions became stuck In Review for several months. Those original products are still stuck, so I now have: Two original subscriptions stuck In Review Two replacement subscriptions stuck Waiting for Review An approved live app with no working subscription products I have contacted Apple Developer Support multiple times, requested escalation and submitted a Feedback Assistant report, but I have not received a resolution. Is it normal for Apple to approve the app version without reviewing the subscriptions included in the same submission? Has anyone found a way to get the subscriptions manually routed to the In-App Purchase review team? This has blocked all subscription revenue for my live app, so I would really appreciate any advice.

Hi everyone, I’m looking for advice because I have run out of ideas. My iOS app has been live for several months, but its original monthly and annual auto-renewable subscriptions have remained stuck In Review the entire time. Because the subscriptions were unavailable in production, users could not start a trial or subscribe. I contacted Apple Developer Support multiple times and the case was escalated, but after more than a month I still had no resolution...ridiculous! I then tried to solve the issue myself: I created two new replacement subscriptions inside the approved subscription group. I completed all pricing, localisation, availability, trial and review information. I imported them into RevenueCat and attached them to the existing entitlement and Offering. I tested both replacement subscriptions successfully in TestFlight. I submitted both subscriptions alongside a new app version. The new app version was approved without any issues. However, Apple did not review the subscriptions with it...again!!! The current statuses are now: Original monthly subscription: In Review Original annual subscription: In Review Replacement monthly subscription: Waiting for Review Replacement annual subscription: Waiting for Review The replacement products work correctly in TestFlight, but the live app cannot load the plans because the products are still unavailable in production. I have submitted multiple support requests, requested urgent escalation and reported the issue through Feedback Assistant, but I am still getting nowhere. Has anyone experienced subscriptions becoming stuck or orphaned in App Store Connect like this? Is there any route that successfully reached the In-App Purchase review team or caused the products to be manually reviewed? This has completely blocked my app’s subscription revenue for months, so any advice would be greatly appreciated.

Hello Apple Developer Community, My app, Apple ID: 6794291305, has been stuck in the “Awaiting Review” status for 5 days now, which seems unusually long compared with the review times I normally expect. I understand that review times can vary and that some submissions may require additional time. However, I’m becoming concerned because we are approaching our marketed release date, and the prolonged review could affect our planned launch. There have been no requests for additional information or other updates regarding the submission so far. Has anyone experienced an app remaining In Awaiting Review for this long recently? Is there anything I should do at this stage, or is it best to continue waiting for the review team to complete the process? Any insight would be greatly appreciated. Thank you.

Hello everyone, I am writing here out of sheer desperation and to seek guidance from the community or any Apple Developer Relations team members who might see this. My Apple Developer account was just terminated abruptly under Section 3.2(f) of the ADP Agreement, with an email citing "documented indications of fraudulent conduct." I am a professional Computer Engineer, a civil servant, and currently a Master's student. I have always taken my development work seriously and strictly adhered to Apple’s guidelines. My entire portfolio consists of legitimate, educational, and utility-based apps. Specifically, I have developed and published: Cogniclash: A straightforward educational trivia/quiz app (geography, flags, general knowledge). Tıpdil / Ringa: Exam preparation and medical terminology tools designed strictly to help medical students and healthcare professionals. Hotstop: A standard, clean utility application. There is absolutely no hidden code, no manipulation of App Store services, and zero fraudulent activity in my apps or my account history. I have already submitted a formal appeal asking the Review Board to share these alleged "documented indications" with me so I can address them, as I strongly believe this is a false flag triggered by an automated system. Being permanently labeled as engaging in "fraudulent acts" is severely damaging to my professional reputation. Has anyone experienced a similar situation where a legitimate account was flagged under 3.2(f)? What is the most effective way to ensure a real human being at the App Review Board actually looks at the apps and the appeal, rather than receiving automated rejections? Any advice or escalation paths would be greatly appreciated. Thank you.

Hello App Review Team, My app has an update that has been submitted for more than a week now. Submission ID: a8d50d9b-b327-4bf6-9a0b-4bab80d6dbdb Previous updates have been reviewed in a day or two max. Kindly let me know if further delay is expected, or if anything is needed from my end. Thank You

My TestFlight build has been in Waiting for Review since June 27, 2026 for more than a month. It was submitted for Beta App Review to enable public testing for external testers. Submission ID: f83d8d76-b239-48a8-8776-e93f4d03d5df Could someone please check whether the submission is stuck or if any additional action is required from my side? Thank you.

We have an app that is updated regularly, and our submissions are typically reviewed within a few hours to one day. We recently submitted an urgent bug fix for a production issue affecting our customers. However, this submission has been stuck in "Waiting for Review" for the past 10 days without any updates. We've opened multiple support tickets, but they've led nowhere. Phone support has also been ineffective, with scheduled callbacks resulting in hours on hold without any progress. What is the appropriate escalation path for a submission that appears to be stalled in the review queue?

I'm looking for advice because I've been facing the same issue with every app submission on my Apple Developer account. Every app I submit remains in "Waiting for Review" for more than one month. The status never changes to "In Review", regardless of the app. Here's what I've already done: Contacted Apple Developer Support. Submitted an Expedited Review request. Waited well beyond the normal review timeframe. Verified that my apps are complete, functional, and comply with the App Store Review Guidelines. The problem is not limited to a single app. It affects every new submission and every app update I send for review. At this point, I'm wondering if there could be an issue with my developer account that is preventing my submissions from entering the review process. Has anyone experienced a similar situation? If so, how was it resolved? If an Apple engineer or App Review team member sees this post, I would be very grateful if someone could check whether there is an issue with my developer account or advise me on what I should do next. Thank you very much for your time and any assistance.

We submitted our iOS app (Apple ID 6504717345) on 2026-07-24. The submission confirmation email says: On average, 50 percent of apps are reviewed in 24 hours and over 90 percent are reviewed in 48 hours. Once we've completed the review, your app's status will be updated and you will be notified. After 6 days, it's still Waiting for Review. Can Apple provide: A reasonable estimate of how long App Review actually takes? Update the E-Mails and/or Website and/or pin a thread here accordingly? If we've made some sort of mistake that's keeping our new update in some stuck state, please advise. Can we get a review, please? Any help is appreciated 🙏

Hello, All of my submissions across my account have been stuck in review for many weeks, which is well outside my normal turnaround. These are apps that have historically been approved within 24 hours or 2-3 days. Those updates are time critical. Singapore MRT just updated on 12 July. We are losing installs and impressions largely because of this, especially no reason is given. App: Singapore MRT Map Route Apple ID: 536957287 / Version: 3.0.1 App: Singapore MRT Map Route(Pro) Apple ID: 475976737 / Version: 3.0.0 App: Epic Cards Battle Apple ID: 1003611640/ Version: 2.6.3 On my side everything appears complete: metadata, build, review notes, demo account credentials, and all agreements in Agreements, Tax, and Banking are accepted. There are no messages in Resolution Center and App Store Connect shows no action required from me. I have contacted Developer Support but have not received a actual response. Could someone please confirm whether these submissions are correctly queued, or whether something is blocking them that requires action on my side? Thank you.

My app was rejected July 16 under Guideline 2.1 (Information Needed) with four questions about the Clinical Health Records API. I replied in full the same day in the Resolution Center, and followed up in that thread on July 22. It has now been 12 days with no response from App Review. I have also contacted Developer Support (case 102942988807), which replied twice but could not provide status on the submission. I have not clicked Resubmit, since Apple's message asked me to reply, and I understand resubmitting closes the correspondence thread. Is there anything further I should be doing, or is a reply alone sufficient to return the submission to the review queue? Submission ID: bc855e56-3ef8-482d-96b0-4380d3fc4a68